Contributors are community members who contribute in concrete ways to the project,
most often in the form of code and/or documentation in the respective project repository. 
Anyone can become a contributor, and contributions can take many forms, other than code contributions, e.g.:
<ul>
    <li>
      <p class="m-0">
        Actively help other users through any of the <a href="#communication-channels">communication channels</a>
        made for that purpose.
      </p>
    </li>
    <li>
        Triage GitHub issues.
    </li>
   <li>
        Organize and collaborate in Selenium meetups, events and conferences.
    </li>
</ul>

<p>
  There is no expectation of commitment to the project, no specific skill requirements,
  and no selection process.
  Some Contributors might have some basic privileges to the GitHub repos to which they have contributed, based on
  their type of contribution (e.g., close an issue after triaging it).
</p>

<p class="pb-4">
  Committers are contributors who have shown that they are committed to the
  continued development of the project through ongoing engagement with the project.
  Committers are given push access to the project's GitHub repos where they
  contribute to. Example getting access to the selenium-docker repository for those contribute to it. 
</p>

<p class="fw-bold">
  Committers:
</p>
<ul>
    <li>
        Should bring their proposals for large changes to the project's code first to
        a GitHub issue, and all relevant committers should be pinged so they can weigh
        in on the discussion if desired.
    </li>
    <li>
        Debates between committers about whether code should be merged should happen
        in GitHub pull requests to keep the project decision history.
    </li>
    <li>
        In general any committer can review and merge a pull request. Committers
        should only merge code they are qualified to review, which might entail pinging
        another committer who has greater ownership over a specific code area.
    </li>
    <li>
        May label and close issues.
    </li>
</ul>

<h4 class="pt-3">Becoming a committer</h4>

<ul>
    <li>
        One must have shown a willingness and ability to participate in the project as
        a team player.
    </li>
    <li>
        Committers are expected to be respectful of every community member and to work
        collaboratively in the spirit of inclusion.
    </li>
    <li>
        Have submitted sufficient substantive contributions to one or more of the
        different projects (Selenium IDE, Docker-Selenium, Selenium Client Bindings, WebSite & Docs). 
        Normally 10 substantive contributions are needed to qualify as a candidate to be a committer, but there
        could be cases where the contributions are substantial enough or technically significant enough that a fewer
        number is also acceptable.
    </li>
</ul>

<div class="row -bg-selenium-cyan-20 justify-content-center">
  <div class="col-12 px-5 pt-5 bg-transparent">
    <h2>Governance Objective</h2>
    Our governance framework is designed to achieve three core objectives:
    <p>
    <p>
    <b>Inclusive Participation</b> 
    <br>We ensure that all individuals, regardless of background or affiliation, have meaningful 
    opportunities to contribute to Selenium's development and direction.
    </p>

    <p>
    <b>Corporate Balance</b>
    <br>We maintain safeguards against undue corporate influence while preventing any single entity 
    from compromising the project's independence or community-driven nature.
    </p>

    <p>
    <b>Reciprocal Value</b>
    <br> We create structures that encourage organizations benefiting from Selenium to contribute back to the 
    project's sustainability and growth.
    </p>

    <br>This document outlines the roles, responsibilities, and processes that define how various 
    types of contributors work within the Selenium project.
    </div>
    </div>

<h2>Roles and Responsibilities</h2>
<ul>
    <li><a href="#users">Users</a></li>
    <li><a href="#contributors">Contributors</a></li>
    ...
    <li><a href="#documenters">Documenters</a></li>
    <li><a href="#translators">Translators</a></li>
    ...
</ul>
...
<h3 id="documenters">Documenters</h3>
<p>...Documenters are community members...given push access...</p>
...
<h3 id="translators">Translators</h3>
<p>...A translator is responsible for all content in a given language...</p>

<h2>Roles and Responsibilities</h2>
<ul>
    <li><a href="#users">Users</a></li>
    <li><a href="#contributors">Contributors</a></li>
    ...
</ul>
...
<h3 id="contributors">Contributors</h3>
<p>
  Contributors are community members who contribute in concrete ways to the project,
  most often in the form of code, documentation, and/or translation.
  Documentation and translation responsibilities include:
  <ul>
    <li>Improving examples and descriptions.</li>
    <li>Creating and updating content for a given language.</li>
    <li>Managing Pull Requests relevant to documentation and language files.</li>
  </ul>
</p>